|
![CPM2C-S1[]0C-DRT Programmable Slaves](CPM2C-S1[]0C-DRT_devicenet_small.jpg)
|

|
* Ordering information
* Specifications
* Configurations
* Dimensions, and etc
|
|
can be found in our PDF brochure.
|
|
Slaves with the Complex
Functionality
Needed for Distributed Blocks
Programmable Slaves combine devices, such as
sensors and actuators, into one functional unit that is treated as a
DeviceNet slave.
Programmable Slaves greatly facilitate device distribution and functional
organization. They help standardize programming between units and reduce
the amount of programming required at the master. I/O and operational
checks can be performed for each functional unit, rather than waiting for
final system assembly, as with conventional distributed I/O systems.
A Programmable Slave can be programmed from
a CX-Programmer up to 3 network levels away. (Includes the DeviceNet
network itself. Possible only with CX-Programmer Ver. 2.1 or later and a
Programmable Slave Ver. 1.04 or later.)
DeviceNet Slave Functions
Multiword I/O links and explicit messages are used to control slaves from
the master. Log data for communications can be sent in one operation
whenever necessary using explicit messages.
CompoBus/S Master Functions
Less wiring is required for terminal block expansions, connections to
remote devices (such as signal lights or pushbutton switches), and
connections to pneumatic valves and other non-OMRON products. Connect
using VCTF cable or Special Flat Cable, which allows easy branching.
RS-232C Communications
Connected to bar code readers, Programmable Terminals, and other devices,
the Programmable Slave processes data locally to reduce the load on the
master.
Expansion Units (3 max.)
Just one Unit is required for each distributed block, reducing the number
of interfaces for multipoint communications to, in turn, reduce costs.
|